Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[resubmission] move NXpid_controller to base_classes #1528

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

lukaspie
Copy link
Contributor

@lukaspie lukaspie commented Jan 9, 2025

This is a follow-up to #1414 where NXpid was mistakenly not included in the vote even though it was originally used within NXactuator. This PR moves NXpid to the base classes and adds it back to NXactuator.

This is a resubmission of #1522 which was marked as merged by GitHub after merging #1414 even though NXpid is not actually part of the base_classes yet.

@lukaspie lukaspie added the NIAC vote needed PR needs an approving vote from NIAC before merge label Jan 9, 2025
@lukaspie lukaspie changed the title move NXpid to base_classes, add in NXactuator [resubmission] move NXpid to base_classes Jan 9, 2025
@phyy-nx
Copy link
Contributor

phyy-nx commented Jan 16, 2025

Telco: it would be nice if this had a bit of clarification at the top. @benajamin volunteered to do this.

Once done, ok to vote.

@lukaspie lukaspie changed the title [resubmission] move NXpid to base_classes [resubmission] move NXpid_controller to base_classes Jan 17, 2025
@lukaspie
Copy link
Contributor Author

@benajamin thanks for volunteering on this, please let me how I can help you. Please note that we renamed the class now to NXpid_controller to avoid any misunderstandings with personal identifiers (also often abrreviated as PIDs).

@lukaspie
Copy link
Contributor Author

@benajamin substantially added to the description of PID controllers in this PR, it should now be ready for review.

@lukaspie lukaspie force-pushed the nxpid branch 2 times, most recently from ce82b0b to b979d33 Compare January 27, 2025 12:26
@phyy-nx
Copy link
Contributor

phyy-nx commented Jan 27, 2025

Thanks @benajamin for the new text

@phyy-nx
Copy link
Contributor

phyy-nx commented Jan 27, 2025

Hi all, as discussed in the Telco, we can now move this PR to an online vote. NIAC committee members please vote on this PR using emojis on this comment. 👍 for yes, 👎 for no, anything else (for example 👀) to abstain. We need 14 votes to hit quorum so please review and vote!

It can also be a link to an ``NXsensor.value`` field.
</doc>
</field>
<field name="K_p_value" type="NX_NUMBER">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems a little odd ending the field names with _value; for example, using K_p instead of K_p_value.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be okay for me, but not sure if covered by the vote here. Maybe could just be done after the vote is in and before the PR is merged.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK with me.

Also we might like to capture some guidelines when naming of fields and groups. I don't think we have these at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NIAC vote needed PR needs an approving vote from NIAC before merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants